Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add aarch64 fdb build & Update lib features #1174

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

vickunwu
Copy link
Contributor

@vickunwu vickunwu commented Feb 7, 2025

This PR finishes building arm64 fdb-variant server as the FoundationDB latest stable release includes the libfdb_c_aarch64.so file.

I also noticed that foundationdb crate has a feature fdb-7_3 since 0.9.0.

Maybe we should consider deprecating the fdb-7_1 feature some day.

These 2 features seems conflicting each other when building. Since it's using libfdb_c_$ARCH.so released in 7.3.x, I think it's better to keep the support of fdb-7_3.


There's also something I want to discuss regarding the last CI refactor.

But I'm not sure whether we should talk it

  • here
  • in previous PR
  • open a new discussion page

@vickunwu vickunwu force-pushed the main branch 3 times, most recently from c806d7a to c3e1825 Compare February 7, 2025 13:47
@mdecimus
Copy link
Member

mdecimus commented Feb 9, 2025

I also noticed that foundationdb crate has a feature fdb-7_3 since 0.9.0.

Great, we can migrate to it as the default. Can this PR be merged?

But I'm not sure whether we should talk it

If it is not related to FDB then please start a new discussion. Thanks!

@vickunwu
Copy link
Contributor Author

Can this PR be merged?

Yes, I think so. It's been successfully compiled. But I am not sure if it's still compatible with FDB 7.1.x.

@mdecimus
Copy link
Member

Please let me know once you're done with the changes and I'll merge.

@vickunwu
Copy link
Contributor Author

vickunwu commented Feb 14, 2025

Sorry. The 2nd commit is supposed to address the image & binary signing issue. Should I open another PR or just change the title of this one?

@mdecimus
Copy link
Member

It's fine, we can use this same PR.

@vickunwu vickunwu force-pushed the main branch 18 times, most recently from 52ac7c0 to 291f8c0 Compare February 18, 2025 13:43
@vickunwu vickunwu marked this pull request as draft February 19, 2025 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants